* This is necessary for pip to be able
  to reference it as the entry point

* Now installing tespeed via `pip install` will
  also kick off a manual read of the
  requirements.txt to install any external deps
* The custom SocksiPy module no longer needs to be
  bundled with tespeed source as it can be just
  installed directly to the env/virtualenv via
  `pip install -r requirements.txt`

* Since the main kickoff code is wrapped
  in an `init` function and called via a
  wrapper (due to pip install), this check
  is no longer needed
* Also did some indentation cleanup to match
  existing codebase

* Also added a manifest file to make
  sure the license is bundled with the
  install

* This will now allow the app to support
  both configurations: running from source
  and running from pip install